[opensuse] (OT) Windows Server 2003 question!
Hi all, As alot of you guys know I'm taking an adult ed class. Well, this morning the school sysop asked me to look at the server, he has a problem. I told him that I don't know Windows, but he said that "you Linux guys know all about networks!" :) Anyway I spent the morning going over the school network. What they have is 13 student workstations, 3 office workstations, 1 server, and 2 network printers. The server has two network cards. Card #1 is to the school network switch, its configured like this: IP 192.168.30.11 Sub 255.255.255.0 Gate 192.168.30.1 DNS 192.168.30.11 Alt DNS 192.168.30.1 Card #2 is to the Internet by a DLS router with a firewall, its configured: IP 192.168.30.10 Sub 255.255.255.0 Gate BLANK DNS 192.168.30.11 Alt DNS 192.168.30.10 The problem is that the server can see and connect to all the workstations and printers. BUT the clients can not see or connect to the server. On the other hand, each client can get to the 'net and can see the printers. Also I pinged the clients and that worked. The clients can see and is connected to the Z: disk on the server, but I can not add the server's Y: disk. Software wise, all the workstations use XP pro SP3 and the server is "Server 2003". Can one of you guys that work with Windows give me an idea or suggestion to fix this? If I can get it fix I'll be golden there! Many Thanks!, JIM -- Jim Hatridge Linux User #88484 Ebay ID: WartHogBulletin ------------------------------------------------------ WartHog Bulletin Info about new German Stamps http://www.WartHogBulletin.de Many Enemies -- Much Honor! Anti-US Propaganda stamp collection http://www.manyenemies-muchhonor.info An American in Bavaria http://www.gaubodengalerie.de -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Thu, Jan 15, 2009 at 11:09 PM, James Hatridge
Hi all, The problem is that the server can see and connect to all the workstations and printers. BUT the clients can not see or connect to the server.
CMIIW this is problem no.1
The clients can see and is connected to the Z: disk on the server, but I can not add the server's Y: disk.
CMIIW this is problem no. 2
Can one of you guys that work with Windows give me an idea or suggestion to fix this? If I can get it fix I'll be golden there!
I don't work with windows :-) But I guess you should share the Y disk and give access to everyone or to domain member if you use Active Directory, and make sure the DNS setup is correct on the server. I don't know if your client can ping the server, but you can enable it by allowing ICMP in the server firewall setting. Hope you will be golden :-) regards, medwinz -- Diogenes - "What I like to drink most is wine that belongs to others." -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
James Hatridge wrote:
Hi all,
As alot of you guys know I'm taking an adult ed class. Well, this morning the school sysop asked me to look at the server, he has a problem. I told him that I don't know Windows, but he said that "you Linux guys know all about networks!" :)
Anyway I spent the morning going over the school network. What they have is 13 student workstations, 3 office workstations, 1 server, and 2 network printers. The server has two network cards.
Card #1 is to the school network switch, its configured like this:
IP 192.168.30.11 Sub 255.255.255.0 Gate 192.168.30.1 DNS 192.168.30.11 Alt DNS 192.168.30.1
Card #2 is to the Internet by a DLS router with a firewall, its configured:
IP 192.168.30.10 Sub 255.255.255.0 Gate BLANK DNS 192.168.30.11 Alt DNS 192.168.30.10
The routing is hosed. Both IPs belong to the same subnet but are connected to different switches. If "File and Printer Sharing" is active on both interfaces then things become really interesting. I had lots of trouble whenever a windows box had two interfaces and both have the "Client for Microsoft Networks" bound to the interface. Disable the second nic and everything should be fine (after a while, since the workstations will have to find out that the Server now only listens on one ip. Afterwards everything should work.
The problem is that the server can see and connect to all the workstations and printers. BUT the clients can not see or connect to the server. On the other hand, each client can get to the 'net and can see the printers. Also I pinged
That proves that the second nic is superfluous. The Windows server does not act as a gateway, so you don't need the second interface.
the clients and that worked. The clients can see and is connected to the Z: disk on the server, but I can not add the server's Y: disk.
Software wise, all the workstations use XP pro SP3 and the server is "Server 2003".
Can one of you guys that work with Windows give me an idea or suggestion to fix this? If I can get it fix I'll be golden there!
Good luck. -- Sandy List replies only please! Please address PMs to: news-reply2 (@) japantest (.) homelinux (.) com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
James Hatridge wrote:
Hi all,
As alot of you guys know I'm taking an adult ed class. Well, this morning the school sysop asked me to look at the server, he has a problem. I told him that I don't know Windows, but he said that "you Linux guys know all about networks!" :)
Anyway I spent the morning going over the school network. What they have is 13 student workstations, 3 office workstations, 1 server, and 2 network printers. The server has two network cards.
Card #1 is to the school network switch, its configured like this:
IP 192.168.30.11 Sub 255.255.255.0 Gate 192.168.30.1 DNS 192.168.30.11 Alt DNS 192.168.30.1
Card #2 is to the Internet by a DLS router with a firewall, its configured:
IP 192.168.30.10 Sub 255.255.255.0 Gate BLANK DNS 192.168.30.11 Alt DNS 192.168.30.10
The problem is that the server can see and connect to all the workstations and printers. BUT the clients can not see or connect to the server. On the other hand, each client can get to the 'net and can see the printers. Also I pinged the clients and that worked. The clients can see and is connected to the Z: disk on the server, but I can not add the server's Y: disk.
Software wise, all the workstations use XP pro SP3 and the server is "Server 2003".
Can one of you guys that work with Windows give me an idea or suggestion to fix this? If I can get it fix I'll be golden there!
Many Thanks!,
JIM
You have 2 cards connected to the same subnet, and you're telling them different things.... The server gets confused when you send something to the 192.168.30.* network, 'cause its got 2 connections to that network... 2 cards would *generally* mean, 2 subnets..... And it also depends on what the DNS/gateway is on the client machines... Good luck! John -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (4)
-
James Hatridge -
John Bennett -
medwinz -
Sandy Drobic