Hi LFS fans,

When I try to join a server I get "did not rec. guest info"
message what is this?

I have S2 and broadband conn.

Ant

how did you solve your problem?
did you get to know the cause?

I am suffering now the same problem

I have the same problem on some server, what is it?

I think it's just when the server is lagging badly, your join request times out sometimes. Unless it's happening with all servers and then you're probably the one with the dodgy connection.

SERVER SUCKS .
Live for speed is going the very bad way. With no server this software has no future. I am a very early LFS registred user and I must say that it has never been so bad !!!!

No Servers? 300 is quite a lot you know...

Quote from anttt69 :

Hi LFS fans,

When I try to join a server I get "did not rec. guest info"
message what is this?

I have S2 and broadband conn.

Ant

I have the same problem, but only on one of my PCs (I have 3 with LFS installed.. 2 demo that I do server admin on, and an S2-unlocked on my AMD64)

The problem only seems to exist on the one I've installed last night. I get the same guest info message as you.

Given that the problem exists on one client and not on 2 others, all connecting to the same server (mine, on a fat pipe in the Docklands in London), it seems clear that the problem is not server-related, nor client-related but in fact PC-related. (All 3 of my LFS installations are the same original zip file)

That doesn't solve the problem, but it does narrow it down significantly. I've killed the Windows firewall to no avail. I will keep trying different possibilities, and when I identify the problem, I will post a solution.

Perhaps a specific net driver is causing this issue?

Quote from the_angry_angel :

Perhaps a specific net driver is causing this issue?

Yes, I agree. Definitely in my case this is as it has transpired. Short answer: Default Gateway.

Here's the solution for any AOL users, using a router to connect multiple PCs to the internet, and having problems with this. (if there even IS anyone!)

Without the AOL software running, this was my config:

C:\>ipconfig /all
Windows IP Configuration
Host Name . . . . . . . . . . . . : piii
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
Ethernet adapter Wireless Network Connection:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : BT Voyager 1040 PCI Adapter
Physical Address. . . . . . . . . : 00-11-F5-18-CB-45
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.0.102
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.0.1
DHCP Server . . . . . . . . . . . : 192.168.0.1
DNS Servers . . . . . . . . . . . : 192.168.0.1
Lease Obtained. . . . . . . . . . : 15 January 2006 18:46:40
Lease Expires . . . . . . . . . . : 22 January 2006 18:46:40

LFS is able to connect to servers with the above setup.

When I loaded AOL and connected to my AOL account, after a few moments my connection to the LFS server died. My network adaptor info has been changed by the AOL client to include the following adaptor in addition to the above:

PPP adapter {38569AD4-8E86-4672-9914-A51C7895491B}:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : WAN (PPP/SLIP) Interface
Physical Address. . . . . . . . . : 00-53-45-00-00-00
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 172.215.198.53
Subnet Mask . . . . . . . . . . . : 255.255.255.255
Default Gateway . . . . . . . . . : 172.215.198.53
DNS Servers . . . . . . . . . . . : 205.188.146.145
NetBIOS over Tcpip. . . . . . . . : Disabled

I disconnected, edited the TCP/IP settings for my local machine to specify both IP address and DNS server (my router, 192.168.0.1):

C:\>ipconfig /all
Windows IP Configuration
Host Name . . . . . . . . . . . . : piii
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
Ethernet adapter Wireless Network Connection:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : BT Voyager 1040 PCI Adapter
Physical Address. . . . . . . . . : 00-11-F5-18-CB-45
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.0.35
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.0.1
DNS Servers . . . . . . . . . . . : 192.168.0.1

I connected to LFS.. all went smoothly... then I loaded AOL in the background, and lost connection to the LFS server.

In the AOL client, I changed the connection method that AOL uses (in Expert Setup) from "Home Network" to "Other Dial up ISP or LAN" (don't ask me what the difference is!) The change appeared to only be the Default Gateway, which with this AOL connection option isn't forced by AOL:

PPP adapter {38569AD4-8E86-4672-9914-A51C7895491B}:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : WAN (PPP/SLIP) Interface
Physical Address. . . . . . . . . : 00-53-45-00-00-00
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 172.202.0.26
Subnet Mask . . . . . . . . . . . : 255.255.255.255
Default Gateway . . . . . . . . . :
DNS Servers . . . . . . . . . . . : 205.188.146.145
NetBIOS over Tcpip. . . . . . . . : Disabled

Success! Now AOL and LFS can co-exist, with no interruptions or problems for either application. LFS connects happily to hosts, with no issues.

I'm sure this problem isn't exclusive to AOL and that many other applications may also force the Default Gateway to a specific remote address. There are ways to force applications to use a specific path, and to avoid using particular software adaptors, but they're typically difficult to implement. Fingers crossed the above might inspire solutions for those already suffering this issue.